This section describes the following tasks:
The first step in setting up an event notification is creating an event destination; after you create an event destination, use the event route modify to associate the event destination with the event or events that you want to be sent to the destination. An event destination consists of a name and one or more destinations for event messages. Possible destinations include e-mail addresses, SNMP clients, and remote syslog daemons.
The following example creates an event destination named admin that sends events to the e-mail address admin@example.com, a remote syslog daemon with the IP address 10.98.27.90, and an SNMP client with the IP address 10.98.12.234.
node::>event destination new -name admin -mail admin@example.com -syslog 10.98.27.90 -snmp 10.98.12.234
To display information about event destinations, use the event destination show command. The command lists the destination name and any e-mail addresses, SNMP clients, and remote syslog daemons associated with the destination.
The following example displays information about all event destinations:
node::>event destination showName Mail Destination Syslog Destination SNMP Destination pager pager@example.com - - criticals sysadmin@example.com - 10.10.4.1, 10.10.5.1 allevents - 10.98.12.234 10.10.4.1, 10.10.5.1 admin admin@example.com 10.98.12.234 10.98.27.90
You can modify an event destination's target e-mail addresses, SNMP client addresses, and syslog daemon addresses by using the event destination modify command. The following example modifies a destination named admin to use SNMP clients with the addresses 10.10.4.1 and 10.10.5.1.
node::>event destination modify -name admin -snmp 10.10.4.1,10.10.5.1